videos.showmethewow.com and videos.systemsarchitectureguild.org now access the SAG YouTube channel
papers.showmethewow.com / papers.systemsarchitectureguild.org redirect to my Academia.edu site
me.showmethewow.com / me.systemsarchitectureguild.org redirects to my LinkedIn profile
The NeMO reference hypermodel 0.8 is released May 21, 2018 (No Magic World Symposium).
Now available on the resource page. See companion video at https://youtu.be/FvWdN0-u_Vk
Developing an architecture with an inferior system modeling tool is like digging the Panama Canal with a teaspoon:
It can be done…but it takes far longer than it should and it is a lot less enjoyable.
The amount of funding to execute system modeling and systems engineering is finite; in many cases, it is zero-sum (or effectively so). To reap the benefits of a competently executed system model, what effort can/should be curtailed to fund the modeling efforts?
Since text-based requirements are, in essence, a textual projection of content that can (and should) be represented in the system model, their development can be delayed without technical penalty.
Instead of churning requirements, author and refine them at widely-spaced knowledge points or reviews. This allows them to be spawned and synchronized with a high-fidelity system model. If you attempt to keep requirements in synch with a rapidly growing and evolving system model you are wasting labor hours (adjudicating changes with all the stakeholder and decision authority drag that entails). Invest that time and effort into a higher-fidelity system model.
Axiom #1: Requirements should be derived from a system model elements; spawn and synchronize them at deliberately-chosen points in the development process.